Dynamically configurable hybrid automatic repeat request (HARQ) configuration

ABSTRACT

A device may determine one or more parameters relating to a network. The device may detect a trigger to alter a hybrid automatic repeat request (HARQ) configuration for the network based on the one or more parameters relating to the network. The device may determine an alteration to the HARQ configuration based on detecting the trigger to alter the HARQ configuration. The device may communicate with a distributed unit or a centralized unit of the network to cause the alteration to the HARQ configuration.

BACKGROUND

Hybrid automatic repeat request (HARQ) protocol is utilized to ensurethat messages are sent reliably from one node to another node in anetwork. For example, HARQ protocol is used to transmit data between aradio access network (RAN) and a user equipment (UE) or a customerpremise equipment (CPE) of a telecommunications network. HARQ designsmay impose latency requirements based on where a HARQ-protocolterminating node is located in the RAN (e.g. in a Centralized Unit (CU)location or in a distributed unit (DU) or remote radio head (RRH)location). The latency requirements may have an impact on connectionsbetween the core network and the RRH or another type of distributed basestation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIGS. 2A and 2B are diagrams of an example environment in which systemsand/or methods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices ofFIGS. 2A and 2B; and

FIG. 4 is a flow chart of an example process for network configurationof a hybrid automatic repeat request (HARQ).

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Automatic repeat request (ARQ) is an error-control method for datatransmission in telecommunications networks. ARQ uses acknowledgements(ACKs) (e.g., messages sent by a receiving node indicating that thereceiving node has correctly received data from the sending node) andtimeouts (e.g., specified periods of time allowed to elapse before anACK is to be received) to achieve reliable data transmission over anunreliable service. If a sending node does not receive an ACK before thetimeout, the sending node may retransmit the data until the sending nodereceives an ACK or exceeds a predefined number of retransmissions.

HARQ is a combination of high-rate forward error-correcting coding andARQ error-control. In standard ARQ, redundant bits are added to data tobe transmitted using an error-detecting (ED) code, such as a cyclicredundancy check (CRC). In HARQ, the original data is encoded with aforward error correction (FEC) code, and parity bits in the FEC areeither immediately sent along with the message or transmitted only uponrequest when a receiving node detects an erroneous message.

HARQ has a fixed set of delay requirements for Long-Term Evolution (LTE)and/or LTE-Advanced (LTE-A) telecommunications networks. For example,LTE/LTE-A telecommunications networks may require a receiving node tosend a HARQ ACK within a particular transmission time interval (TTI).The TTI may vary based on where the HARQ functionality is located in thenetwork, such as in a back-haul of the network, a mid-haul of thenetwork, or a front-haul of the network. As a consequence, the HARQdelay requirements may limit network architectures and services. Inother words, network architectures and services may be limited to thosethat satisfy HARQ delay requirements.

Implementations, described herein, may dynamically configure HARQparameters based on multiple parameters. For example, HARQ parametersmay be dynamically configured based on front-haul/back-haul transportnetwork capabilities (e.g., bandwidth, latency, or the like), based onan underlying radio access network (RAN) split or a dynamicallyconfigured RAN split, based on network slicing, based on user equipment(UE) capabilities, based on an application quality of service (QoS)requirement, or the like. Moreover, implementations, described herein,may dynamically configure HARQ parameters based on network metrics(e.g., HARQ ACK timing, a number of HARQ processes, a number of HARQrepetitions, or the like.). For example, implementations, describedherein, may dynamically configure HARQ parameters to accommodate anobserved TTI regardless of where the HARQ functionality is located inthe network. Furthermore, implementations, described herein, maydynamically configure HARQ parameters to enable particular use cases.For example, HARQ parameters may be dynamically configured for anextreme fixed/mobile broadband use case, a massive Internet of Things(IoT) use case, an ultra-low latency use case, or the like.

In this way, flexibility is improved for network architectures andnetwork deployments, thereby improving network performance and reducingcost relative to a static network architecture and deployment.Additionally, network performance is improved as a result of enablingincreased centralization of network resources and/or functionalities forRRHs. In this way, a flexible RAN split of functionalities between acentralized unit and a distributed unit of a network is enabled byconfiguring HARQ based on a network configuration, a networkarchitecture, a use case, a network slice, a performance requirement, orthe like, which enables, relative to a static RAN, reduced utilizationof computing resources (e.g., processing resources, memory resources,and/or energy resources), cost efficient design, or the like.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. Example implementation 100 includes a network, whichincludes a network management device, a core network, a RAN, and an RRH.The RAN includes a centralized unit and a distributed unit. Thecentralized unit communicates with the core network via a back-haul. Thecentralized unit communicates with the distributed unit via a mid-haul.The distributed unit communicates with the RRH via a front-haul.

As further shown in FIG. 1, the network management device determines anetwork configuration or a use case. For example, based on detecting atrigger (e.g., input, from a network operator to a client device, thatis communicated to the network management device; determining that anetwork metric satisfies a threshold; or determining an alteration to anetwork architecture or a network deployment), the network managementdevice may determine a network configuration or a use case, and maydetermine to alter a HARQ configuration based on the networkconfiguration or the use case. The network management device may alter aHARQ configuration based on the network configuration or the use case.For example, the network management device may alter an ACK time, aquantity of processes, a quantity of repetitions, or the like for theHARQ protocol being used by the network. In this way, the networkmanagement device uses a dynamic HARQ configuration to enable networkarchitectures and network deployments to be flexible. Additionally, thenetwork management device uses the dynamically configurable HARQ toenable better network performance because additional centralization ofnetwork resources for RRHs is permitted.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIGS. 2A and 2B are diagrams of an example environment 200 in whichsystems and/or methods, described herein, may be implemented. As shownin FIG. 2A, environment 200 may include one or more wireless devices205-1 through 205-N (N≥1) (hereinafter referred to collectively as“wireless devices 205,” and individual as “wireless device 205”); a basestation 210; a mobility management entity device (MME) 215; a servinggateway (SGW) 220; a packet data network gateway (PGW) 225; a networkmanagement device 230; a home subscriber server (HSS) 235; and anauthentication, authorization, and accounting server (AAA) 240. Devicesof environment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

Some implementations are described herein as being performed within anLTE network for explanatory purposes. Some implementations may beperformed within a network that is not an LTE network, such as a thirdgeneration (3G) network, a fourth generation (4G) network, a fifthgeneration (5G) network, or the like.

Environment 200 may include an evolved packet system (EPS) that includesa 4G or 5G radio access network (e.g., an LTE network and/or an evolvedpacket core (EPC) that operate based on a third generation partnershipproject (3GPP) wireless communication standard). For example, the LTEnetwork may include a RAN that includes one or more base stations 210that take the form of evolved Node Bs (eNBs) via which wireless device205 communicates with the EPC. The EPC may include MME 215, SGW 220, PGW225, and/or network management device 230 that enable wireless device205 to communicate with the network and/or an Internet protocol (IP)multimedia subsystem (IMS) core. The IMS core may include HSS 235 and/orAAA 240, and may manage device registration and authentication, sessioninitiation, or the like, associated with wireless devices 205. HSS 235and/or AAA 240 may reside in the EPC and/or the IMS core.

Wireless device 205 includes one or more devices capable ofcommunicating with base station 210 and/or a network. For example,wireless device 205 may include a wireless communication device, aradiotelephone, a personal communications system (PCS) terminal (e.g.,that may combine a cellular radiotelephone with data processing and datacommunications capabilities), a smart phone, a laptop computer, a tabletcomputer, a personal gaming system, and/or a similar device. Wirelessdevice 205 may send traffic to and/or receive traffic from the network(e.g., via base station 210, SGW 220, and/or PGW 225). In someimplementations, wireless device 205 may include a user device type ofwireless device 205, such as a user equipment (UE), a mobile device, orthe like. Additionally, or alternatively, wireless device 205 mayinclude a machine device type of wireless device, such as an Internet ofThings (IoT) type of device, a Category M1 (Cat-M1) device, a narrowband IoT (NB-IoT) device, or the like. In some implementations, wirelessdevice 205 may be associated with a particular QoS classification.

Base station 210 includes one or more devices capable of transferringtraffic, such as audio, video, text, and/or other traffic, destined forand/or received from wireless device 205. In some implementations, basestation 210 may include an eNB associated with the LTE network thatreceives traffic from and/or sends traffic to the network via SGW 220and/or PGW 225. Additionally, or alternatively, one or more basestations 210 may be associated with a RAN that is not associated withthe LTE network. Base station 210 may send traffic to and/or receivetraffic from wireless device 205 via an air interface. In someimplementations, base station 210 may include a small cell base station,such as a base station of a microcell, a picocell, and/or a femtocell.

MME 215 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with wireless device 205. In someimplementations, MME 215 may perform operations relating toauthentication of wireless device 205. Additionally, or alternatively,MME 215 may facilitate the selection of a particular SGW 220 and/or aparticular PGW 225 to serve traffic to and/or from wireless device 205.MME 215 may perform operations associated with handing off wirelessdevice 205 from a first base station 210 to a second base station 210when wireless device 205 is transitioning from a first cell associatedwith the first base station 210 to a second cell associated with thesecond base station 210. Additionally, or alternatively, MME 215 mayselect another MME (not pictured), to which wireless device 205 shouldbe handed off (e.g., when wireless device 205 moves out of range of MME215).

SGW 220 includes one or more devices capable of routing traffic. Forexample, SGW 220 may include one or more data processing and/or traffictransfer devices, such as a gateway, a router, a modem, a switch, afirewall, a network interface card (NIC), a hub, a bridge, a serverdevice, an optical add/drop multiplexer (OADM), or any other type ofdevice that processes and/or transfers traffic. In some implementations,SGW 220 may aggregate traffic received from one or more base stations210 associated with the LTE network, and may send the aggregated trafficto the network (e.g., via PGW 225) and/or other network devicesassociated with the EPC and/or the IMS core. SGW 220 may also receivetraffic from the network and/or other network devices, and may send thereceived traffic to wireless device 205 via base station 210.Additionally, or alternatively, SGW 220 may perform operationsassociated with handing off wireless device 205 to and/or from an LTEnetwork.

PGW 225 includes one or more devices capable of providing connectivityfor wireless device 205 to external packet data networks (e.g., otherthan the depicted EPC and/or LTE network). For example, PGW 225 mayinclude one or more data processing and/or traffic transfer devices,such as a gateway, a router, a modem, a switch, a firewall, a NIC, ahub, a bridge, a server device, an OADM, or any other type of devicethat processes and/or transfers traffic. In some implementations, PGW225 may aggregate traffic received from one or more SGWs 220, and maysend the aggregated traffic to the network. Additionally, oralternatively, PGW 225 may receive traffic from the network, and maysend the traffic to wireless device 205 via SGW 220 and base station210. PGW 225 may record data usage information (e.g., byte usage), andmay provide the data usage information to AAA 240.

Network management device 230 includes one or more devices capable ofmanaging a network. For example, network management device 230 mayinclude a server that controls a configuration of one or more networkdevices (e.g., one or more wireless devices 205, one or more basestations 210, or one or more devices described herein with regard toFIG. 2B), such as a HARQ configuration. In some implementations, networkmanagement device 230 may control one or more parameters relating to theHARQ configuration, such as a latency requirement, a HARQ ACK timing, aquantity of processes for HARQ, a quantity of repetitions for HARQ, orthe like. In some implementations, network management device 230 mayreside in base station 210. For example, network management device 230may be a self-organizing network (SON) functionality of base station210. In some implementations, network management device 230 may residein another device, such as one or more devices described herein withregard to FIG. 2B.

HSS 235 includes one or more devices, such as one or more serverdevices, capable of managing (e.g., receiving, generating, storing,processing, and/or providing) information associated with wirelessdevice 205. For example, HSS 235 may manage subscription informationassociated with wireless device 205, such as information that identifiesa subscriber profile of a user associated with wireless device 205,information that identifies services and/or applications that areaccessible to wireless device 205, location information associated withwireless device 205, a network identifier (e.g., a network address) thatidentifies wireless device 205, information that identifies a treatmentof wireless device 205 (e.g., quality of service information, a quantityof minutes allowed per time period, a quantity of data consumptionallowed per time period, or the like.), and/or similar information. HSS235 may provide this information to one or more other devices ofenvironment 200 to support the operations performed by those devices.

AAA 240 includes one or more devices, such as one or more serverdevices, that perform authentication, authorization, and/or accountingoperations for communication sessions associated with wireless device205. For example, AAA 240 may perform authentication operations forwireless device 205 and/or a user of wireless device 205 (e.g., usingone or more credentials), may control access, by wireless device 205, toa service and/or an application (e.g., based on one or morerestrictions, such as time-of-day restrictions, location restrictions,single or multiple access restrictions, read/write restrictions, or thelike.), may track resources consumed by wireless device 205 (e.g., aquantity of voice minutes consumed, a quantity of data consumed, or thelike.), and/or may perform similar operations.

As shown in FIG. 2B, example environment 200 includes the EPC core(e.g., a core network); a RAN, which includes a centralized unit 250 anda distributed unit 255; and base station 210, which includes a remoteradio head (RRH) 260. Centralized unit 250 and distributed unit 255 mayrefer to portions of the RAN architecture in which variousfunctionalities may reside (e.g., where a server or another type ofnetwork device may perform the various functionalities). For example,centralized unit 250 may include a server, a cluster of servers, a cloudserver, a server farm, or the like that is located at a centralizedlocation and performs processing for multiple distributed units 255and/or RRHs 260. In this case, centralized unit 250 may communicate withthe EPC core via a back-haul connection and may communicate withdistributed unit 255 via a mid-haul connection. Similarly, distributedunit 255 may refer to a server that is located within a thresholdproximity of RRH 260. In this case, distributed unit 255 may communicatewith RRH 260 via a front-haul connection. RRH 260 may refer to a portionof a base station 210 (e.g., a transceiver). For example, centralizedunit 250 and distributed unit 255 may perform various functionalities ofbase station 210 relating to transmitting and/or receiving networktraffic, and may utilize RRH 260 as an air interface for transmittingand/or receiving.

In some implementations, a RAN split of functionalities betweencentralized unit 250 and distributed unit 255 may be associated with aportion of a layer. For example, using a flexible RAN split may causeone or more functionalities of Layer 3 (e.g., radio resource control(RRC) functionalities or Internet Protocol (IP) functionalities), Layer2 (e.g., packet data convergence protocol (PDCP) functionalities, radiolink control (RLC) functionalities, or medium access control (MAC)functionalities), Layer 1 (e.g., bit processing functionalities,modulation functionalities, radio element mapping functionalities), or aradio frequency interface (e.g., common public radio interface (CPRI) toradio frequency (RF) modulation functionalities) to be performed bycentralized unit 250 or distributed unit 255 based on a processingrequirement, a latency requirement, or the like, as described herein. Inthis way, a flexible RAN split of functionalities between centralizedunit 250 and distributed unit 255 based on a network configuration, anetwork architecture, a use case, a network slice, a performancerequirement, or the like may enable, relative to a static RAN, reducedutilization of computing resources (e.g., processing resources, memoryresources, and/or energy resources), cost efficient design, or the like.

The number and arrangement of devices and networks shown in FIGS. 2A and2B are provided as an example. In practice, there may be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan those shown in FIGS. 2A and 2B. Furthermore, two or more devicesshown in FIGS. 2A and 2B may be implemented within a single device, or asingle device shown in FIGS. 2A and 2B may be implemented as multiple,distributed devices. Additionally, or alternatively, a set of devices(e.g., one or more devices) of environment 200 may perform one or morefunctions described as being performed by another set of devices ofenvironment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to wireless device 205, base station 210, MME 215, SGW220, PGW 225, network management device 230, HSS 235, AAA 240,centralized unit 250, distributed unit 255, and/or RRH 260. In someimplementations, wireless device 205, base station 210, MME 215, SGW220, PGW 225, network management device 230, HSS 235, AAA 240,centralized unit 250, distributed unit 255, and/or RRH 260 may includeone or more devices 300 and/or one or more components of device 300. Asshown in FIG. 3, device 300 may include a bus 310, a processor 320, amemory 330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 takesthe form of a processor (e.g., a central processing unit (CPU), agraphics processing unit (GPU), and/or an accelerated processing unit(APU)), a microprocessor, a microcontroller, and/or any processingcomponent (e.g., a field-programmable gate array (FPGA) and/or anapplication-specific integrated circuit (ASIC)) that interprets and/orexecutes instructions. In some implementations, processor 320 includesone or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for networkconfiguration of a HARQ. In some implementations, one or more processblocks of FIG. 4 may be performed by network management device 230. Insome implementations, one or more process blocks of FIG. 4 may beperformed by another device or a group of devices separate from orincluding network management device 230, such as wireless device 205,base station 210, MME 215, SGW 220, PGW 225, HSS 235, AAA 240,centralized unit 250, distributed unit 255, or RRH 260.

As shown in FIG. 4, process 400 may include detecting a trigger to altera HARQ configuration (block 410). For example, network management device230 may detect a trigger to alter a HARQ configuration. In someimplementations, network management device 230 may detect the triggerbased on an instruction from a network operator. For example, a clientdevice may receive an input via a user interface from a networkoperator, and the client device may transmit the instruction to networkmanagement device 230 to alter a HARQ configuration. In this way,network management device 230 may reduce utilization of computingresources relative to determining a network metric and/or detecting atrigger.

In some implementations, network management device 230 may detect thetrigger based on determining that a network metric satisfies a thresholdvalue. For example, network management device 230 may determine that aparticular network metric (e.g., based on receiving information fromnetwork monitoring equipment, a set of probes that monitor networkperformance indicators, or the like), such as a network throughput, aquantity of network traffic, a bit error rate, a quantity of droppedpackets, or the like, satisfies a threshold value, and may determine toalter the HARQ configuration. In this way, network management device 230may reduce a period of time to alter the HARQ configuration based onutilization of the network relative to utilizing another type oftrigger. In some implementations, network management device 230 maydetect the trigger based on determining that an alteration to a networkarchitecture or network deployment has occurred. For example, networkmanagement device 230 may determine that a RAN split has been altered(e.g., a division of functionalities of the RAN between centralized unit250 and distributed unit 255 has been altered), and may determine toalter the HARQ configuration based on determining that the RAN split hasbeen altered. In this case, network management device 230 may determinethat the alteration to the network architecture or network deploymenthas occurred based on identifying a change to a network configurationfile or database (e.g., based on determining that a date of modificationof the network configuration file or database is changed). In this way,network management device 230 may ensure that the HARQ configurationpermits the altered RAN split to operate.

Additionally, or alternatively, network management device 230 maydetermine (e.g., based on identifying a change to a networkconfiguration file or a database) that a configuration relating to afront-haul, mid-haul, or back-haul connection transport networkcapability (e.g., a bandwidth requirement or capability, a latencyrequirement or capability, a throughput requirement or capability, anerror correction requirement or capability, or the like) has beenaltered, and may determine to alter the HARQ configuration. In thiscase, network management device 230 may determine the alteration to theHARQ protocol used for the particular connection. Additionally, oralternatively, network management device 230 may determine an alterationto a network slicing (e.g., based on monitoring network controlsignaling, such as during setup of a slice or during dynamicreconfiguration of a slice), an alteration to wireless device 205capabilities, an alteration in a quantity of network traffic QoS for anapplication, or the like, and may alter the HARQ configuration. In someimplementations, network management device 230 may set the HARQconfiguration at an initial startup (e.g., of network management device230 or of the network). For example, when the network is established,network management device 230 may determine a network architecture ofthe network and may set the HARQ configuration based on the networkarchitecture of the network.

In some implementations, network management device 230 may determine toalter the HARQ configuration for a particular portion of a network. Forexample, network management device 230 may determine to alter the HARQconfiguration for a particular network layer (e.g., Layer 1 (L1), Layer2 (L2), Layer 3 (L3), or a radio frequency (RF) layer), a particularcentralized unit 250-distributed unit 255 pair, a particular link, aparticular geographic area, or the like. In some implementations,network management device 230 may determine to alter the HARQconfiguration for a particular network slice (e.g., a 5G logical networkslice that includes a set of logical network resources for a particularuse case) for a particular use case (e.g., a mobile broadband use case,an IoT use case, a 4G use case, a 5G use case, or the like), to enable aparticular machine-type communication (e.g., an IoT devicecommunication), to enable a critical machine type communication (e.g.,an emergency services communication), or the like. In this case, networkmanagement device 230 may detect a trigger to include multiple HARQconfigurations for the multiple network slices (e.g., multiple logicalnetwork slices sharing a common physical RAN). In some implementations,the particular use case may include a fixed broadband use case, a mobilebroadband use case, a massive IoT use case (e.g., a quantity of IoTdevices satisfying a threshold at a particular location), an ultra-lowlatency use case (e.g., a latency requirement satisfying a threshold),or the like.

As further shown in FIG. 4, process 400 may include determining analteration to a HARQ configuration based on detecting the trigger toalter the HARQ configuration (block 420). For example, networkmanagement device 230 may determine an alteration to a HARQconfiguration based on detecting the trigger to alter the HARQconfiguration.

In some implementations, network management device 230 may determinethat an alteration to a set of HARQ parameters, such as a HARQ ACKtiming parameter or the like, is necessary. For example, although a 4Gnetwork may require a 4 millisecond HARQ ACK time and a 5G network mayrequire a less than 4 millisecond HARQ ACK time, network managementdevice 230 may determine that a use case of the network is forcommunications for which a greater than 4 millisecond HARQ ACK timeresults in satisfactory network performance. In this case, networkmanagement device 230 may relax a HARQ ACK timing requirement to agreater than 4 millisecond requirement. In some implementations, networkmanagement device 230 may determine an alteration to a quantity of HARQprocesses, an alteration to a quantity of repetitions for HARQ, analteration to whether the HARQ be performed in centralized unit 250 ordistributed unit 255, or the like.

In some implementations, network management device 230 may determine analteration for the HARQ based on a use case, based on a networkarchitecture, based on a network metric (e.g., to improve networkperformance), based on an instruction from a network operator (e.g.,indicating what to alter), or a combination of one or more criteria.

As further shown in FIG. 4, process 400 may include altering the HARQconfiguration based on determining the alteration to the HARQconfiguration (block 430). For example, network management device 230may alter the HARQ configuration based on determining the alteration tothe HARQ configuration.

In some implementations, network management device 230 may cause networkdevices (e.g., centralized unit 250, distributed unit 255, devices of acore network, or the like) to utilize the altered HARQ configuration.For example, when network management device 230 determines that there isto be an alteration to the HARQ ACK timing, network management device230 may cause centralized unit 250 to utilize a relaxed HARQ ACK timingrequirement (e.g., a greater than 4 second HARQ ACK timing requirement).Similarly, network management device 230 may cause centralized unit 250and/or distributed unit 255 to utilize an altered quantity of HARQprocesses, an altered quantity of HARQ repetitions, or the like.

In some implementations, network management device 230 may cause one ormore network devices to utilize the HARQ configuration for a particularportion of the network. For example, when network management device 230determines that there is to be an alteration to the HARQ configurationfor a particular layer (e.g., Layer 1, Layer 2, or Layer 3), networkmanagement device 230 may cause distributed unit 255 to utilize thealtered HARQ configuration for the particular layer. In this waygranularity of control of a network is improved relative to utilizing asingle HARQ configuration for each portion of a network. Additionally,or alternatively, when network management device 230 determines thatthere is to be an alteration to the HARQ based on a network slice, thennetwork management device 230 may cause distributed unit 255 to utilizethe altered HARQ configuration for the network slice. Additionally, oralternatively, when network management device 230 determines that thereis to be an alteration to the HARQ based on a particular use case (e.g.,a mobile broadband use case or an IoT use case), a particular type ofcommunication (e.g., an IoT machine type communication or an emergencyservices communication), or the like, network management device 230 maycause distributed unit 255 to utilize the altered HARQ configuration forthe particular use case. For example, distributed unit 255 may change astored HARQ ITT parameter to adjust the HARQ configuration. Similarly,distributed unit 255 may change a quantity of concurrent HARQ processesthat may be performed.

In some implementations, network management device 230 may cause networkdevices to utilize the HARQ configuration based on a networkarchitecture. For example, when network management device 230 determinesthat there has been an alteration to the HARQ based on a RAN split(e.g., a change to the division of functionalities of the RAN betweencentralized unit 250 and distributed unit 255), then network managementdevice 230 may cause centralized unit 250 and one or more distributedunits 255 to utilize the altered HARQ configuration. In this case, thecentralized unit 250 may utilize a first HARQ configuration for a firstone or more distributed units 255 (e.g., associated with a first set ofparameters, such as a particular use case or network metric) and asecond HARQ configuration for a second one or more distributed units 255(e.g., associated with a second set of parameters, such as anotherparticular use case or network metric).

In some implementations, network management device 230 may cause networkdevices to utilize the HARQ configuration based an instruction from anetwork operator. For example, when network management device 230determines that there has been an alteration to the HARQ based on aninstruction from a network operator, then network management device 230may cause centralized unit 250 or distributed unit 255 to utilize thealtered HARQ configuration according to the instruction of the networkoperator.

In some implementations, network management device 230 may perform avalidation procedure based on causing the network devices to utilize theHARQ configuration. For example, network management device 230 maydetermine that network performance is not adversely impacted by the HARQconfiguration by monitoring network performance for a threshold periodof time. In some implementations, network management device 230 mayrevert the HARQ configuration based on determining that networkperformance is adversely impacted.

In some implementations, network management device 230 may continue tomonitor to detect a trigger to alter the HARQ configuration. Forexample, network management device 230 may monitor the network to obtainone or more network parameters, may monitor a network configuration fileor a database to determine a network architecture or a networkdeployment, or the like, and based on detecting a trigger relating tothe monitoring, network management device 230 may determine another HARQconfiguration for the network.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

In this way, network management device 230 enables utilization offlexible network architectures and network deployments. Additionally, oralternatively, based on permitting utilization of flexible networkarchitectures and network deployments, network management device 230improves network performance, relative to a static network architectureand a static network deployment, based on permitting improvedcentralization of network resources for a first set of network use casesand distribution of network resources for a second set of network usecases.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, or the like.), and may be used interchangeably with“one or more.” Where only one item is intended, the term “one” orsimilar language is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: a memory; and one or moreprocessors to: detect a trigger to alter a hybrid automatic repeatrequest (HARQ) configuration for a network based on a determination thatan alteration to a network architecture or network deployment hasoccurred; select a HARQ parameter relating to the HARQ configurationthat is to be altered based on detecting the trigger to alter the HARQconfiguration; determine a first HARQ configuration for a first logicalnetwork slice and a second HARQ configuration for a second logicalnetwork slice based on selecting the HARQ parameter; and communicatewith one or more network devices of the network to cause the one or morenetwork devices to implement the first HARQ configuration for the firstlogical network slice and the second HARQ configuration for the secondlogical network slice.
 2. The device of claim 1, where the HARQparameter includes: a HARQ acknowledgement (ACK) timing parameter, aquantity of HARQ processes, or a quantity of HARQ repetitions.
 3. Thedevice of claim 1, where the one or more processors are further to:determine a transport network capability of the network; and where theone or more processors, when determining the first HARQ configurationand the second HARQ configuration, are to: determine the first HARQconfiguration and the second HARQ configuration based on the transportnetwork capability of the network.
 4. The device of claim 3, where thetransport network capability includes at least one of: a bandwidthcapability, or a latency capability.
 5. The device of claim 1, where theone or more processors are further to: determine a radio access network(RAN) split of the network; and where the one or more processors, whendetermining the first HARQ configuration and the second HARQconfiguration, are to: determine the first HARQ configuration and thesecond HARQ configuration based on the RAN split.
 6. The device of claim1, where the one or more processors are further to: determine a use casefor the network; and where the one or more processors, when determiningthe first HARQ configuration and the second HARQ configuration, are to:determine the first HARQ configuration and the second HARQ configurationbased on the use case.
 7. The device of claim 6, where the one or moreprocessors further to: determine a bandwidth requirement or a latencyrequirement of the use case; and where the one or more processors, whendetermining the first HARQ configuration and the second HARQconfiguration, are to: determine the first HARQ configuration and thesecond HARQ configuration based on the bandwidth requirement or thelatency requirement of the use case.
 8. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors, cause the one or more processors to: determine one or moreparameters relating to a network; detect, based on a determination thatan alteration to a network architecture or network deployment hasoccurred and based on the one or more parameters relating to thenetwork, a trigger to alter a hybrid automatic repeat request (HARQ)configuration for the network; determine a first HARQ configuration fora first logical network slice and a second HARQ configuration for asecond logical network slice based on detecting the trigger to alter theHARQ configuration for the network; and communicate with a distributedunit or a centralized unit of the network to cause the distributed unitor the centralized unit to implement the first HARQ configuration forthe first logical network slice and the second HARQ configuration forthe second logical network slice.
 9. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,that cause the one or more processors to determine the one or moreparameters, cause the one or more processors to: determine a set ofnetwork metrics associated with the network, the set of network metricsincluding at least one of: a network throughput, a quantity of networktraffic, a bit error rate, or a quantity of dropped packets.
 10. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions, that cause the one or more processors to determinethe one or more parameters, cause the one or more processors to:determine a division of radio access network (RAN) functionalitiesbetween the centralized unit and the distributed unit; where the one ormore instructions, that cause the one or more processors to detect thetrigger to alter the HARQ configuration, cause the one or moreprocessors to: determine that the division of RAN functionalities ischanged from a previous division of RAN functionalities; and where theone or more instructions, that cause the one or more processors todetermine the first HARQ configuration and the second HARQconfiguration, cause the one or more processors to: determine the firstHARQ configuration and the second HARQ configuration based ondetermining that the division of RAN functionalities is changed from theprevious division of RAN functionalities.
 11. The non-transitorycomputer-readable medium of claim 10, where the division of RANfunctionalities includes a split of at least one of: Layer 3 (L3)functionalities, Layer 2 (L2) functionalities, Layer 1 (L1)functionalities, or radio frequency (RF) functionalities.
 12. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions, that cause the one or more processors to determinethe first HARQ configuration and the second HARQ configuration, causethe one or more processors to: determine the first HARQ configurationand the second HARQ configuration based on a latency requirement or abandwidth requirement relating to the network.
 13. The non-transitorycomputer-readable medium of claim 8, where the HARQ configuration forthe network relates to a HARQ protocol used for at least one of: aback-haul connection, a mid-haul connection, or a front-haul connection.14. The non-transitory computer-readable medium of claim 8, where theone or more instructions, when executed by the one or more processors,further cause the one or more processors to: communicate with a networkdevice of a core network or with a remote radio head to cause analteration to the HARQ configuration.
 15. A method, comprising:detecting, by a device and based on a determination that an alterationto a network architecture or network deployment has occurred, a triggerto alter a hybrid automatic repeat request (HARQ) configuration for anetwork, the network including a radio access network (RAN) thatincludes a centralized unit and a distributed unit to perform a set offunctionalities relating to transmitting information and receivinginformation; selecting, by the device and based on detecting thetrigger, a set of HARQ parameters relating to the HARQ configurationthat is to be altered; determining, by the device, a first HARQconfiguration for a first logical network slice and a second HARQconfiguration for a second logical network slice based on selecting theHARQ parameter; and communicating, by the device, with at least one ofthe centralized unit or the distributed unit to cause the at least oneof the centralized unit or the distributed unit to implement the firstHARQ configuration for the first logical network slice and the secondHARQ configuration for the second logical network slice.
 16. The methodof claim 15, further comprising: determining an alteration to a networkcapability of the network or a use case for the network; and altering,by the device, the set of HARQ parameters for the network based on thealteration to the network capability or the use case for the network.17. The method of claim 15, where selecting the set of HARQ parameterscomprises: selecting a first set of HARQ parameters for a first portionof the network and a second set of HARQ parameters for a second portionof the network, the first portion of the network being different fromthe second portion of the network.
 18. The method of claim 16, where thenetwork capability is a capability of at least one of: a back-haulconnection of the network, the back-haul connection connecting a corenetwork and the centralized unit; a mid-haul connection of the network,the mid-haul connection connecting the centralized unit and thedistributed unit; or a front-haul connection of the network, thefront-haul connection connecting the distributed unit and a remote radiohead.
 19. The method of claim 16, where the use case includes at leastone of a 4G use case or a 5G use case.
 20. The device of claim 1, wherethe one or more processors are further to: determine the alteration tothe network architecture or the network deployment based on identifyinga change to a configuration file or a database.